You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OKF Graph Wiki — Agent-Maintained Knowledge Graph for Context Retrieval
OKF Graph Wiki — Agent-Maintained Knowledge Graph for Context Retrieval
I've been running Andrej Karpathy's LLM Wiki
pattern for several months — reading sources, compiling them into a
compounding, git-diffable wiki instead of re-deriving everything from
scratch every session — and I'm a genuine convert. But two things kept
nagging at me: query salience (finding the right page reliably, not
just something plausible) and token economy (not re-reading half the
wiki to answer one question).
Platforms: Linux and Windows 11 tested by us; macOS reported by others.
Tested on Claude Code 2.1.257–2.1.317. The binary is not modified (BUN_OPTIONS=--preload). An update can silently undo it, so see Verify.
TL;DR
Every ~30 seconds, Claude Code re-sends each background agent's full transcript to the model to
A hands-on one semester course where students build their own compiler from scratch, starting from elementwise programs and ending with training SOTA LLMs on GPUs. This course aggressively builds on the previous week, and is an exercise in slop management. If you let any slop in early, it will compound and you will not finish the class.
Course description: This course covers the design and implementation of a modern machine learning compiler, and examines the interaction between IR design, hardware capabilities, and the structure of machine learning programs. Topics covered include term rewriting, code generation, movement operators, kernel fusion, memory hierarchies, GPU architecture, automatic differentiation, and flash attention. It is a project course, providing experience with performance-oriented programming, managing a codebase that grows all semester, and working in 1 or 2 person teams, culminating in a compiler capable of training modern LLMs.
Keep in mind that getting your hands on a premium font does not mean you have the legal right to use it. It's probably really hard to check, but I personally wouldn't use a pirated font for professional use. It should, however, be fine for personal use. I am not responsible for any legal action taken against you.
Using Search Engines
Any search engine should work with this method.
Choose the font you want to download. Googling for specific types of fonts may help.
You might even find that the font is free to download!
Search the font like this: [Font name].ttf or [Font name].otf
You can add site:vk.com, site:github.com, or site:onlinewebfonts.com in your search in order to broaden your search results.
Click on one of the links and click Download/View Raw (GitHub).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
The core idea
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
My (seemingly successful?) attempt to root-cause the severe CPU/RAM usage issues and multi-second jankiness for GitHub.com on Firefox.
Why the fuck is GitHub so janky on Firefox lately?
Note: I didn't use AI to write this. I originally had it try to analyze the profiler GC logs, but there wasn't enough information for it to be conclusive (see below).